- database_credentials is a top level key. The next key will be a datastore. This could be MySQL or Cassandra or anything else.
  Each data store (dstore) contains a name, eg {mysql: ['cred1', 'cred2']}.
  These credentials point to a vault path under /dstore/mysql/{cred1,cred2}
  These passwords are then mapped to the paasta service as a volume, where each file corresponds to a Vault entry

…ames

- Used a context manager for temporarily setting vault credentials
- Several python magic upgrades
- Added sample return types for data
- Changed default parameters to required for dstore/creds
- Few refactors

- Changed database and dstore -> datastore for clarity

- set_env always resets the environ later, so it should instead be renamed to reflect this

- Although we didn't specify cassandra here (since we don't know yet), we add additional_properties = True to suffice

- Having one volume with keys + paths as items from SecretSource allows us to get the same effect
- Refactored time.sleep in tests and secrets_sync
- Fixed test cases to match

Co-authored-by: Luis Pérez <[email protected]>

- Shortened volume name for datastores

…_volume_name

…ased-mysql-password-rotation

- Corrected 'help' for --secret-type call